-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added ability to invite user as owner #938
Conversation
# Conflicts: # src/hooks/api/ownerships.ts # src/i18n/nl.json # src/pages/organizers/[organizerId]/ownerships/index.page.tsx
# Conflicts: # src/hooks/api/ownerships.ts # src/i18n/nl.json # src/pages/organizers/[organizerId]/ownerships/index.page.tsx
const ownershipId = error.body.detail.split('with id ')[1]; | ||
await approveRequestedOwnership(ownershipId); | ||
} else { | ||
setError('email', { message: error.body.detail || error.title }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@simon-debruijn I did this originally to cascade the email errors back to the user UI, but ended up reverting it to a generic since but it allowed users to probe for existing emails in the system, but now it's sometimes cryptic why an email is rejected. Do you think we should show the actual errors?
Added
Waiting for cultuurnet/udb3-backend#1847 to wrap up
Ticket: https://jira.publiq.be/browse/III-6358